This option is available if you have chosen the Evaluation or Shareware
implementation.
The Custom/Secure Evaluation mode requires a registration before the
end-user can evaluate the application. It provides higher security for
evaluation software. Particularly, the end-user may intend to format the harddisk in order to re-evaluate the evaluation software.
Doing so causes the application to generate a new Registration ID, and the
end-user must register again. You would not give out the License Key for one
who frequently registers for software evaluation.
The General Evaluation mode is used by most evaluation software. The
end-user can use the application right away without registration, until the
evaluation period ends. However, this mode cannot prevent the end-user to
re-format the harddisk, and re-evaluate the
application again and again.
You can enable limits for the evaluation. These limits will be
effective when the protected application is first run. The evaluation expires
whenever a limit has been reached.
·
Expired Date. Specify an expiration date. The format is dd/mm/yyyy.
·
Max-Day. Specify the maximum number of days that the application can operate.
·
Max-Exec. Specify the maximum number of executions that the application can
operate.
In the General Evaluation mode, the user can try out the evaluation
version of the application right after installation, until the evaluation period
is expired. In case you issue a new evaluation release (still using the same
Program ID), when the user updates the application to the new release, by
default the evaluation period is not extended. In this situation, the user
would need to obtain an evaluation License Key to extend the evaluation period
and try the new release.
By using the evaluation release feature, you can allow the user to
update the evaluation version, and start a new evaluation period without having
to obtain an evaluation License Key. In this case, you must assign a release
number in the Eval Release field, and
enable the Update release checkbox. As a result, when the user updates
the evaluation version with a higher release number than the existing one, the
Key of the protected application will be updated that automatically starts a
new evaluation period. In case the user updates the evaluation version with a
lower or the same release number, the Key will not be updated (i.e. no change
to the remaining evaluation period).
See Also